-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
CI: Test Pyarrow Less #46386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: Test Pyarrow Less #46386
Conversation
.github/workflows/posix.yml
Outdated
- env_file: actions-38.yaml | ||
pattern: "not single_cpu" | ||
pyarrow_version: 5 | ||
name: "Min Pyarrow" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the min pyarrow is actually 1.0.1, better just to name this like "Pyarrow v5"
- env_file: actions-38.yaml | ||
pattern: "not single_cpu" | ||
pyarrow_version: 7 | ||
name: "Latest Pyarrow" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this eventually won't be the latest, similar better to name this "Pyarrow v7"
This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this. |
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.CI has been really clogged w/ 2-3hr queue times.
Cut down on number of builds by only testing Pyarrow on one python version(if behavior is different based on Python version, that is pyarrow's problem).
If compat continues to be an issue in the future, I would suggest that pyarrow test a "pandas-dev" build, similar to our numpydev builds. I have added one of these builds to fastparquet in the past, and it seems to be effective as there haven't been any recent issues with new fastparquet versions breaking CI IIRC.